🌐 Web query:

Do GitHub Actions on.push.branchesfilters use glob patterns or regular expressions, and would the pattern[0-9]+.x.xmatch a branch named12.x.x?

💡 Result:

GitHub Actions on.push.branches filters use glob patterns, not regular expressions. The pattern [0-9]+.x.x would NOT match the branch named 12.x.x. In GitHub Actions glob patterns (powered by @actions/glob using minimatch): - [] matches exactly ONE character from the specified set or range (e.g., [0-9] matches a single digit 0-9). - + is a literal character, not a quantifier (unlike regex where + means "one or more"). It does not repeat the preceding element. - Therefore, [0-9]+ matches exactly one digit (0-9) followed by a literal + character. For 12.x.x: - Position 1: 1 (matches [0-9]) - Position 2: 2 (does NOT match literal +) - No match.

Citations:

• 1: https://docs.github.com/actions/using-workflows/workflow-syntax-for-github-actions
• 2: https://docs.github.com/actions/reference/workflow-syntax-for-github-actions
• 3: https://zenn.dev/gloriali/scraps/aa4cbe7e387dc8
• 4: https://www.npmjs.com/package/@actions/glob
• 5: Match numeric range isaacs/node-glob#325
• 6: https://stackoverflow.com/questions/68078004/why-doesnt-my-github-action-trigger-on-a-regex-tag

🏁 Script executed:

# Verify the actual content at line 15 of the workflow file
if [ -f ".github/workflows/automated-translations.yml" ]; then
  echo "=== File content around line 15 ==="
  sed -n '10,20p' .github/workflows/automated-translations.yml | cat -n
else
  echo "File not found"
fi

Repository: blackbaud/skyux

Length of output: 324

Learnt from: johnhwhite
Repo: blackbaud/skyux PR: 4381
File: .github/workflows/automated-translations.yml:15-15
Timestamp: 2026-04-17T11:19:33.262Z
Learning: In GitHub Actions `on.push.branches` (and similar) filter patterns, `+` is a special character meaning "one or more of the preceding element" (extended glob semantics), not a literal character. For example, `[0-9]+.x.x` correctly matches multi-digit version branch names like `12.x.x`. This is confirmed by the GitHub Actions documentation which lists `+` as a special glob character in branch filter patterns.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

🌐 Web query:

In GitHub Actions pull_request_targetworkflows, isgithub.head_ref unique across different forks, or is it only the source branch name?

💡 Result:

In GitHub Actions pull_request_target workflows, github.head_ref is the source branch name (e.g., "feature-branch"), not a unique identifier across different forks. It is only the branch name from the head of the pull request, regardless of whether the PR originates from the same repository or a fork. To distinguish forks, use github.event.pull_request.head.repo.full_name != github.repository or check github.event.pull_request.head.repo.fork.

Citations:

• 1: https://gist.github.com/toshimaru/f14386ab69394e6ffb54aa799b9b124b
• 2: https://docs.github.com/en/actions/reference/workflows-and-actions/contexts
• 3: https://stackoverflow.com/questions/62331829/how-to-get-the-target-branch-of-the-github-pull-request-from-an-actions
• 4: https://stackoverflow.com/questions/70775445/determining-the-origin-repo-of-pull-request-in-workflow-yaml

🏁 Script executed:

cat -n .github/workflows/e2e.yml | head -50

Repository: blackbaud/skyux

Length of output: 2129

🏁 Script executed:

cat -n .github/workflows/e2e.yml | grep -A 2 -B 2 "group:"

Repository: blackbaud/skyux

Length of output: 1804

-  group: ${{ github.workflow }}-${{ github.event_name == 'push' && github.run_number || github.head_ref || github.ref_name }}
+  group: ${{ github.workflow }}-${{ github.event_name == 'push' && github.run_number || format('{0}-{1}', github.event.pull_request.number || github.run_id, github.head_ref || github.ref_name) }}

Apply the same PR-specific discriminator to the job-level concurrency.group values at lines 46, 114, 159, 219, and 427.

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

🌐 Web query:

For pull_request_targetworkflows, what dogithub.repositoryandgithub.head_refresolve to on forked PRs, and how doesactions/checkoutuse therepositoryandref inputs together?

💡 Result:

In pull_request_target workflows, which run in the context of the base repository (even for forked PRs): - github.repository resolves to the base repository (e.g., "owner/base-repo"), as the workflow executes in the base repo's context. This is consistent across all events, including forked PRs, since pull_request_target workflows run against the base branch's code and context. - github.head_ref resolves to the source branch name from the PR's head (e.g., "feature-branch"). This is available for both pull_request and pull_request_target events. For actions/checkout: - The repository input defaults to ${{ github.repository }} (base repo). - The ref input defaults to the reference or SHA that triggered the workflow (for pull_request_target, typically the base branch's ref/SHA, like "refs/heads/main"). To checkout the PR's head commit from a fork, explicitly set repository: ${{ github.event.pull_request.head.repo.full_name }} and ref: ${{ github.head_ref }} or ${{ github.event.pull_request.head.sha }}. This allows fetching from the fork using the workflow's GITHUB_TOKEN (which has access to the base repo but can fetch public forks or same-org forks). Note: Never run untrusted PR code in pull_request_target without validation, as it has access to secrets.

Citations:

• 1: https://docs.github.com/en/actions/reference/contexts-reference
• 2: https://docs.github.com/actions/using-workflows/events-that-trigger-workflows
• 3: https://stackoverflow.com/questions/64802322/running-github-actions-on-the-code-in-a-pull-request-from-a-fork
• 4: https://stackoverflow.com/questions/70775445/determining-the-origin-repo-of-pull-request-in-workflow-yaml
• 5: https://github.com/actions/checkout
• 6: https://github.com/actions/checkout/blob/main/README.md

🏁 Script executed:

cat -n .github/workflows/e2e.yml | head -70

Repository: blackbaud/skyux

Length of output: 2955

🏁 Script executed:

cat -n .github/workflows/e2e.yml | tail -n +100

Repository: blackbaud/skyux

Length of output: 25052

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

🌐 Web query:

In PowerShell, do native command failures like git rebaseorgit pushstop script execution by default, or do scripts need to check$LASTEXITCODE/ enable$PSNativeCommandUseErrorActionPreference explicitly?

💡 Result:

By default, native command failures like git rebase or git push (non-zero exit codes) do not stop PowerShell script execution. Scripts must explicitly check $LASTEXITCODE after such commands (e.g., if ($LASTEXITCODE -ne 0) { throw }), or enable integration with PowerShell's error handling by setting $PSNativeCommandUseErrorActionPreference = $true (PowerShell 7.3+). With this set to $true (opt-in, default is $false) and $ErrorActionPreference = 'Stop', non-zero exit codes trigger a terminating error that stops execution. This behavior differs from PowerShell cmdlets, where $ErrorActionPreference = 'Stop' (default: 'Continue') stops on non-terminating errors without extra steps. Official docs confirm: $PSNativeCommandUseErrorActionPreference default is $false (about_Preference_Variables). Multiple sources (StackOverflow, GitHub issues, blogs) emphasize manual $LASTEXITCODE checks are traditionally required for external commands like git. Example to stop on native failure: $ErrorActionPreference = 'Stop' $PSNativeCommandUseErrorActionPreference = $true git push # Stops script if non-zero exit code Without $PSNativeCommandUseErrorActionPreference = $true, use: git push if ($LASTEXITCODE -ne 0) { throw "git push failed with exit code $LASTEXITCODE" }

Citations:

• 1: https://stackoverflow.com/questions/57468522/powershell-and-process-exit-codes
• 2: https://matthorgan.xyz/blog/powershell-handling-native-applications/
• 3: Native error handling: $PSNativeCommandUseErrorActionPreference = $true unexpectedly causes non-terminating, not statement-terminating errors PowerShell/PowerShell#18368
• 4: Switch $PSNativeCommandUseErrorActionPreference to $true when feature is enabled PowerShell/PowerShell#18695
• 5: PSNativeCommandUseErrorActionPreference default value is $false MicrosoftDocs/PowerShell-Docs#10752
• 6: https://stackoverflow.com/questions/67743279/how-to-get-exit-code-from-powershell-script
• 7: https://stackoverflow.com/questions/67743279/how-to-get-exit-code-from-powershell-script/67743340
• 8: https://stackoverflow.com/questions/57468522/powershell-and-process-exit-codes/57468523
• 9: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_preference_variables
• 10: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_preference_variables?view=powershell-7.5
• 11: https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_preference_variables?view=powershell-7.4
• 12: https://stackoverflow.com/questions/9948517/how-to-stop-a-powershell-script-on-the-first-error
• 13: https://www.meziantou.net/stop-the-script-when-an-error-occurs-in-powershell.htm
• 14: https://stackoverflow.com/questions/11450153/powershell-analogue-of-bashs-set-e

🏁 Script executed:

# First, locate and examine the script file
find . -name "automated-translations.ps1" -type f

Repository: blackbaud/skyux

Length of output: 95

🏁 Script executed:

# Get the file size first
wc -l ./scripts/automated-translations.ps1

Repository: blackbaud/skyux

Length of output: 99

🏁 Script executed:

# Check lines 75-85 to see context around the git rebase (lines 79-80)
sed -n '75,85p' ./scripts/automated-translations.ps1 | cat -n

echo "---"

# Check lines 125-135 to see context around git push (lines 129-130)
sed -n '125,135p' ./scripts/automated-translations.ps1 | cat -n

echo "---"

# Check if $PSNativeCommandUseErrorActionPreference is set anywhere
rg 'PSNativeCommandUseErrorActionPreference' ./scripts/automated-translations.ps1

echo "---"

# Check for $LASTEXITCODE usage in the script
rg 'LASTEXITCODE' ./scripts/automated-translations.ps1

Repository: blackbaud/skyux

Length of output: 923

🏁 Script executed:

# Check the beginning of the script for any error handling setup
head -20 ./scripts/automated-translations.ps1 | cat -n

echo "---"

# Check if there's any overall error handling pattern in the script
rg 'ErrorActionPreference|exit|throw' ./scripts/automated-translations.ps1

Repository: blackbaud/skyux

Length of output: 603

🏁 Script executed:

# Let's verify the exact lines mentioned in the review by showing more context
sed -n '76,85p' ./scripts/automated-translations.ps1 | cat -n

echo "---"

# Check the lines around the push command more carefully
sed -n '126,135p' ./scripts/automated-translations.ps1 | cat -n

Repository: blackbaud/skyux

Length of output: 826